Skip to content

feat(field): switch canonical route configurations - #4314

Merged
EvenSol merged 1 commit into
masterfrom
codex/4228-route-configurations
Oct 13, 2026
Merged

EvenSol merged 1 commit into
masterfrom
codex/4228-route-configurations

Conversation

@EvenSol

@EvenSol EvenSol commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Add named multi-edge route configurations to the existing live FieldWellNetworkProcessUnit and canonical LoopedPipeNetwork.

This does not introduce another topology, hydraulic solver, optimizer, schedule, or cost model.

Engineering behavior

The synthetic live-well acceptance case uses one canonical graph with a primary two-edge path, a higher-resistance brownfield two-edge path, and a dual-path looped configuration. It verifies:

  • process-automation discovery/read/write;
  • lower deliverability and higher well backpressure on the restrictive brownfield path;
  • positive flow through both branches in the redundant configuration;
  • coupled network mass conservation;
  • exact restoration of the primary operating point;
  • unchanged hydraulic model selection;
  • independent copied selector state; and
  • fail-closed overlap, fractional-selection, and non-binary-state checks.

This is implementation plus synthetic integration/conservation/trend evidence. It is not field, laboratory, commercial-simulator, outage, brownfield, IPR/VLP, or hydraulic-correlation qualification.

Validation

Exact published commit: d0c8a432dfb858c9404b53dd91bb7d4d9ce930b2
Exact published tree: 7dd565dd58e96cce6821ea42186387a0aafd7c6b
Base: 7dc323b9bfc917f1fb000655857d316140605975

Passed locally:

  • 111 adjacent JUnit tests; 0 failures/errors/skips:
    • FieldWellNetworkProcessUnitTest (5)
    • FieldToFacilityOptimizationAcceptanceTest (2)
    • FieldNetworkScaleAcceptanceTest (3)
    • ProcessAutomationTest (101)
  • Spotless apply/check;
  • Checkstyle;
  • documentation search (788 Markdown, 1 HTML);
  • generated engineering coverage --check (3,376 public types);
  • PMD report generation; no new violation on the added configuration paths (repository baseline remains);
  • git diff --check.

Local Javadocs were blocked by infrastructure because the runtime contains Java 17 JRE only and no javac/javadoc executable. Exact-head hosted Java 21 Javadocs and Java 8/21 model-specification jobs passed. The broader fast/slow matrix and remaining workflow groups are still running. The local pre-commit executable is absent; the exact-head hosted pre-commit workflow passed and mandatory direct gates were run. Keep this PR draft until all exact-head CI, review, and unresolved-thread checks complete.

Documentation impact

Updated the SURF integration guide and pipeline/network skill with the multi-edge line-up contract, automation address, validation boundary, and dependency-ordered continuation. Generated engineering coverage was refreshed.

Coordination

Next dependency

Exercise these configurations on the larger live production/injection field cases with qualified pump/compressor maps, shared host constraints, controlled reservoir-pressure updates, and lifecycle evidence. Independently qualify thermal/ST-F101/F109 route cases before design use.

Refs #4228, #4188, #3154, #2911, #3298, #3153, #2899, #1332.

Add transactional named multi-edge line-ups for direct, brownfield, and redundant-loop paths on the existing live field topology. Expose categorical ProcessAutomation actions while preserving per-edge hydraulic models, exact rollback, and the compatible exclusive-route API.

Refs #4228, #4188, #3154
@EvenSol
EvenSol force-pushed the codex/4228-route-configurations branch from 4bea7ab to d0c8a43 Compare October 12, 2026 18:46
@EvenSol
EvenSol marked this pull request as ready for review October 13, 2026 04:33
@EvenSol
EvenSol merged commit d27433c into master Oct 13, 2026
32 checks passed
@EvenSol
EvenSol deleted the codex/4228-route-configurations branch October 13, 2026 04:33
EvenSol added a commit that referenced this pull request Oct 13, 2026
Invalidate accepted-point envelope evidence after route or operating-limit revisions, rerun only the declared dependency chain, and persist a replacement only after the existing production guard accepts fresh evidence. Expose current/stale evidence in the living report and cover #4314 route configuration changes plus fail-closed guard behavior.

Refs #4188, #3154, #4187, #2939
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant